Welcome to the SyslogX ActiveX Control Page

SyslogX is an ActiveX Control that allows a VB 4.0, VB 5.0 or any other program capable of utilizing ActiveX controls to send log messages to the syslog daemon on unix systems. This control is the perfect solution for a mixed Unix/Microsoft environment. By allowing programs that are Microsoft Windows based to log messages to the same facilities that Unix processes log to, monitoring of complex processing environments can be centralized and more easily tracked.

The SyslogX control supports the full set of Unix syslog priorities and facilities. In addition, SyslogX allows the sending of log messages to a log file on the local machine, the inclusion of a standard header to identify the process sending the message, a time stamp that is based on the local time of the machine sending the message. An audible alert can also be generated, as an additional way for the machine to attract attention to itself if there is problem.

Using SyslogX

To successfully use SyslogX you will need to properly configure a machine running a syslog daemon and of course install the software on a machine that will SyslogX. If you are not the administrator of the machine running the syslog daemon, you should inform your network administrator of what you are doing. He/She may not appreciate messages from unexpected sources appearing in their log files.

The machine running the syslog daemon may need to have its syslog.conf file modified depending on the priority and facility being used. On some machines the syslog daemon may also need to be configured to accept remote logging messages. If you do not have root access on the target machine, you will need to get your systems administrator to make the modifications.

After installing SyslogX on your machine, include the SyslogX control in your main application, set the destination the message is to be sent to and use the LogMsg method to send the message. Multiple instances of SyslogX can be included in your application if necessary.

Generally you will only want to send messages of importance to the syslog facility. This minimizes the load on the logging machine and avoids cluttering the log files with useless information that can make troubleshooting more difficult.

Methods and Properties

Properties

DestIP- The address of the machine that is running a syslog daemon. This can be a numeric address or DNS name. A numeric address is preferable since a failed DNS lookup can cause delays. String Value.

Enabled- The SyslogX control will send messages to the syslog daemon. Boolean

Facility- The Syslog facility that the message will be sent to. List Selection.

Priority- The priority of the message. List Selection.

FileLogName- The name of a local file to send log messages to.String Value.

FileLogEnable- Enable the sending of log messages to a local file. Boolean Value.

Header- A standard header that will be included at the start of every log message sent. String Value.

ShowTime- Include the local time of the machine in the message. Boolean Value.

AlertEnable- Allow the generation of an audible alert when a message is sent.A additional way to get a machine to attract attention to itself if there is problem. If a sound card is not installed, then the internal speaker is used. Boolean Value.

AlertSound-Allows you to specify the name of a .wav file to use or leave blank for no sound. String Value.

Methods

LogMsg- Send a log message to the syslog daemon.

Limitations on the Unregistered Version

This unregistered version of SyslogX is limited to printing 50 messages before stopping. This should give you adequate opprotunity to test the control and decide if it meets you needs. A warning dialog box is also display when the first message is sent.

Registration

The RegNet ID number is not available yet. When you are ready to register return to the SyslogX Control Home page at http://www.telepath.com/brantley/SyslogX/index.htm

Click here for more information on licesning, distribution and support